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

[FW] 14 better scripts lul #2197

Closed
wants to merge 4 commits into from
Closed

Conversation

fw-bot
Copy link
Collaborator

@fw-bot fw-bot commented Mar 9, 2023

Description:

description of this task, what is implemented and why it is implemented that way.

Odoo task ID : TASK_ID

review checklist

  • feature is organized in plugin, or UI components
  • support of duplicate sheet (deep copy)
  • in model/core: ranges are Range object, and can be adapted (adaptRanges)
  • in model/UI: ranges are strings (to show the user)
  • undo-able commands (uses this.history.update)
  • multiuser-able commands (has inverse commands and transformations where needed)
  • new/updated/removed commands are documented
  • exportable in excel
  • translations (_lt("qmsdf %s", abc))
  • unit tested
  • clean commented code
  • track breaking changes
  • doc is rebuild (npm run doc)
  • status is correct in Odoo

Forward-Port-Of: #2191

@robodoo
Copy link
Collaborator

robodoo commented Mar 9, 2023

@fw-bot
Copy link
Collaborator Author

fw-bot commented Mar 9, 2023

@LucasLefevre @rrahir cherrypicking of pull request #2191 failed.

stdout:

Auto-merging package.json
CONFLICT (content): Merge conflict in package.json

stderr:

09:11:46.377967 git.c:455               trace: built-in: git cherry-pick 80d4fc19d29b765a48940e7468bb91a2e27aa623
error: could not apply 80d4fc19... [IMP] package: add task label
hint: After resolving the conflicts, mark them with
hint: "git add/rm <pathspec>", then run
hint: "git cherry-pick --continue".
hint: You can instead skip this commit with "git cherry-pick --skip".
hint: To abort and get back to the state before "git cherry-pick",
hint: run "git cherry-pick --abort".
----------
status:

Either perform the forward-port manually (and push to this branch, proceeding as usual) or close this PR (maybe?).

In the former case, you may want to edit this PR message as well.

LucasLefevre and others added 4 commits March 9, 2023 10:29
Add the task label before every log line in the console.
This helps to know what is logging what.

The current task \"build:* -- --watch\" is split into smaller
task without argument. Otherwise, the labels would also include
the argument, making it very long
[build:js -- --watch] => [watch:ts]

the "serve" task is also rename to better reflect what it does:
serving static files.
In v15, we also have a "server" task which could be confusing
Currently, every file is watched by the static server.
including typescript files and intermediary js files.
But the static server only cares about the bundle file
and demo files.
In v15, a collaborative server was introduced.
This server can raise errors (let's say if it cannot start because the port
is already used).

In the current situation, errors are cleared by ts watch mode.
This makes it difficult to see and know what happened.
Exit events that are fired following an error of exectuion were silently
caught. This would hide the reason of failure and make it very difficult
to know what happened.
@rrahir rrahir force-pushed the 15.0-14-better-scripts-lul-pIxZ-fw branch from 5e73310 to 398c72b Compare March 9, 2023 09:51
@rrahir
Copy link
Collaborator

rrahir commented Mar 9, 2023

@robodoo r+

robodoo pushed a commit that referenced this pull request Mar 9, 2023
Add the task label before every log line in the console.
This helps to know what is logging what.

The current task \"build:* -- --watch\" is split into smaller
task without argument. Otherwise, the labels would also include
the argument, making it very long
[build:js -- --watch] => [watch:ts]

the "serve" task is also rename to better reflect what it does:
serving static files.
In v15, we also have a "server" task which could be confusing

Part-of: #2197
robodoo pushed a commit that referenced this pull request Mar 9, 2023
Currently, every file is watched by the static server.
including typescript files and intermediary js files.
But the static server only cares about the bundle file
and demo files.

Part-of: #2197
robodoo pushed a commit that referenced this pull request Mar 9, 2023
In v15, a collaborative server was introduced.
This server can raise errors (let's say if it cannot start because the port
is already used).

In the current situation, errors are cleared by ts watch mode.
This makes it difficult to see and know what happened.

Part-of: #2197
robodoo pushed a commit that referenced this pull request Mar 9, 2023
Exit events that are fired following an error of exectuion were silently
caught. This would hide the reason of failure and make it very difficult
to know what happened.

closes #2197

Signed-off-by: Rémi Rahir (rar) <rar@odoo.com>
@fw-bot fw-bot mentioned this pull request Mar 9, 2023
14 tasks
@robodoo robodoo temporarily deployed to merge March 9, 2023 10:02 Inactive
@robodoo robodoo closed this Mar 9, 2023
@fw-bot fw-bot deleted the 15.0-14-better-scripts-lul-pIxZ-fw branch March 23, 2023 10:47
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.

None yet

4 participants