Closed Sadaf-A closed 11 months ago
Name | Link |
---|---|
Latest commit | c9b8780176ca76e2b7998877ba4aae3387f01b17 |
Latest deploy log | https://app.netlify.com/sites/ubiquibot-staging/deploys/650d064fe7f3330008d7818d |
Deploy Preview | https://deploy-preview-761--ubiquibot-staging.netlify.app |
Preview on mobile | Toggle QR Code...Use your smartphone camera to open QR code link. |
To edit notification comments on pull requests, go to your Netlify site configuration.
1/ You should not change the name of ubiquibot-config.yml 2/ I can see no changes in config names. 3/ Please make sure you mark the PR
ready for review
once done.
i changed price-multiplier
to priceMultiplier
and could you please elaborate a little on where are the config names that I am supposed to change
Shouldn't you change every config name
Shouldn't you change every config name
I'm sorry but not able to understand can you link the file?
We should change every config name in ubiquibot-config.yml and codebase to read them in src/utils/private.ts
Maybe also in default config json file
Maybe also in default config json file
True
bump @EtherealGlow cause its blocking other PR from the merge.
In the recent merge, we've changed the default config filename from *.json
to *.ts
. would you get the changes into your branch? @Sadaf-A
In the recent merge, we've changed the default config filename from
*.json
to*.ts
. would you get the changes into your branch? @Sadaf-A
sure, I'll get to it right now
same feeling yeah. so my idea is to create a sync PR from development to main as soon as this PR merged.
I am gonna handle the merge and hotfix if needed tomorrow morning.
@rndquu would you open the config PRs in both ubiquity and ubiquibot org for the upcoming changes?
@rndquu would you open the config PRs in both ubiquity and ubiquibot org for the upcoming changes?
I remember pavlovcik explicitly stated that the config should be kebab-case hence this refactoring was implemented. You 100% sure that we should migrate to camel case?
From my point of view it looks like that every 6 months we refactor the bot's config from camel case to kebab case and back which doesn't bring any advantages.
Its kind of back and forth but I hope this would be the final one in case
changes.
Its kind of back and forth but I hope this would be the final one in
case
changes.
We need @pavlovcik's review for this PR
@rndquu would you open the config PRs in both ubiquity and ubiquibot org for the upcoming changes?
I remember pavlovcik explicitly stated that the config should be kebab-case hence this refactoring was implemented. You 100% sure that we should migrate to camel case?
From my point of view it looks like that every 6 months we refactor the bot's config from camel case to kebab case and back which doesn't bring any advantages.
I vaguely recall a discussion we had where it was decided to finally change everything into camelCase recently because the only software that consumes this configuration file is the UbiquiBot typescript code, which expresses the same properties in camelCase.
CI doesn’t pass but the rest seem fine.
I'll fix that right away!
CI doesn’t pass but the rest seem fine.
ok will handle the merge after the conflicts are resolved. This should be a top priority task because it blocks some PRs right now.
The next steps:
https://github.com/ubiquibot/ubiquibot-config/pull/8 https://github.com/ubiquity/ubiquibot-config/pull/15
requested a review from @rndquu
merging the both config PRs.
795
sync PR
merged
I had quick QAs once I merged the relevant PRs. Here are the QA issues.
Staging: https://github.com/ubiquibot/staging/issues/179 Production: https://github.com/ubiquibot/production/issues/65
So far looks good to me.
Finally
kebab case to camel case
Resolves #711