Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Response of /api.json will be incorrect after the first request #15293

Open
1 task done
zyoshoka opened this issue Jan 16, 2025 · 0 comments · May be fixed by #15294
Open
1 task done

Response of /api.json will be incorrect after the first request #15293

zyoshoka opened this issue Jan 16, 2025 · 0 comments · May be fixed by #15294
Labels
⚠️bug? This might be a bug

Comments

@zyoshoka
Copy link
Contributor

💡 Summary

/api.json のレスポンスは、2回目のリクエスト以降おかしくなります。

🥰 Expected Behavior

2回目のリクエスト以降においても、UserLite スキーマの required には isBot が含まれない

🤬 Actual Behavior

2回目のリクエスト以降においては、UserLite スキーマの required に isBot が含まれてしまう

📝 Steps to Reproduce

No response

💻 Frontend Environment



🛰 Backend Environment (for server admin)


* Installation Method or Hosting Service:
* Misskey: 2025.1.0-beta.1
* Node:
* PostgreSQL:
* Redis:
* OS and Architecture:


Do you want to address this bug yourself?


    

  •  Yes, I will patch the bug myself and send a pull request
    • 


      		
    

      
  





        



            

              
            

        

      


      
    








      


  




  
  

              

  
    Sign up for free
    to join this conversation on GitHub.
    Already have an account?
    Sign in to comment


  



  






  
                  




    

  


      
  

    Assignees
  



        

    No one assigned







      


  


  

    Labels
  



    

      

    ⚠️bug?

  This might be a bug








      

  

    

        

    Projects
  


        




        
  

    

      
          
        [実験中] 管理用
    

    

      

            
    Status: Todo


      

    

    

  







  



      


  

    
  

    Milestone
  


      No milestone





    
      
          


  

    
      

        
    

    Development
  




          
  
Successfully merging a pull request may close this issue.





    


  
          
      fix(backend): clone schema before converting to OAS schema to avoid mutation

    
      zyoshoka/misskey
    





    
  




      

    

  
      

  

    

      1 participant
    

    

        
          @zyoshoka