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.

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

[mod] use ask key for display_text instead and support i18n #697

Merged
merged 1 commit into from
Apr 2, 2019

Conversation

Psycojoker
Copy link
Member

The problem

While working on the admin integration I realized that uniformizing the behavior with other key and using "ask" instead of "text" was way simpler for the whole code (despite not making that much sens for "display_text" field) and annex tool (i18n integration for example).

I also added i18n support.

PR Status

Ready to merge.

How to test

Use this app and try to install it https://github.com/Psycojoker/display_text_ynh

Validation

  • Principle agreement 0/2 :
  • Quick review 0/1 :
  • Simple test 0/1 :
  • Deep review 0/1 :

@alexAubin
Copy link
Member

smol change, yolomergin'

@alexAubin alexAubin merged commit 1c7aadd into stretch-unstable Apr 2, 2019
@alexAubin alexAubin deleted the manifest_texte_argument branch April 2, 2019 00:04
@Psycojoker
Copy link
Member Author

@YunoHost/apps just to inform you about the final format ^

@maniackcrudelis
Copy link
Contributor

Final format of that #669, I guess ?

So it would be that: ?

{
    "name": "some_text",
    "type": "display_text",
    "ask": "This is some text that is going to be displayed.\n\nAnother line."
},

With ask instead of text

@Psycojoker
Copy link
Member Author

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

Successfully merging this pull request may close these issues.

3 participants