-
Notifications
You must be signed in to change notification settings - Fork 276
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
Vueify config-postprocessing #4259
Conversation
@@ -0,0 +1,378 @@ | |||
<script type="text/x-template" id="name-pattern-tempate"> | |||
<div id="name_pattern_wrapper"> | |||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Was this extra line intentional?
</label> | ||
</div> | ||
<div id="naming_key" class="nocheck" v-if="showLegend"> | ||
<table class="Key"> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This should be using 2 spaces like the rest of the HTML.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ive used 4 spaces for all now.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ah, this is
8 I think, double indented?
} | ||
}, | ||
mounted() { | ||
this.namingPattern = this.pattern; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Please switch to this.
const { pattern } = this;
this.namingPattern = pattern;
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
You could also add namingPattern
and presets
here so you're not setting anything directly to this.*
.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
But why? You go from one line to two lines of code. What is the benefit of this?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Just the same reason you'd use a const anywhere else.
If you use this.
you can still set it to another value which is wrong since you should be using the store or local data. If you're using a const there's no issue there and it makes it more clear that you're import read-only
data.
…eify-postprocessing
@@ -290,16 +309,16 @@ const startVue = () => { | |||
<fieldset class="component-group-list"> | |||
|
|||
<!-- default name-pattern component --> | |||
<name-pattern :pattern="pattern" :presets="presets"></name-pattern> | |||
<name-pattern :enabled="true" :naming-pattern="pattern" :naming-presets="presets" :multi-ep-style="multiEpSelected" :multi-ep-styles="multiEpStrings" @change="onChangePattern" ></name-pattern> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Since this is the default why not move this data to the components data object as default values?
Prob merge conflict.
…eify-postprocessing # Conflicts: # medusa/server/api/v2/config.py # themes-default/slim/views/config_postProcessing.mako # themes-default/slim/views/layouts/main.mako # themes/dark/templates/config_postProcessing.mako # themes/dark/templates/layouts/main.mako # themes/light/templates/config_postProcessing.mako # themes/light/templates/layouts/main.mako
… component. Moved mako python to apiv2 / vue. Started bootstrapping the postprocessing page.
<span class="component-title">Metadata Type:</span> | ||
<span class="component-desc"> | ||
<span>Metadata Type:</span> | ||
<span > |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Missed a space here.
medusa/server/api/v2/config.py
Outdated
@@ -92,6 +92,19 @@ def get(self, identifier, path_param=None): | |||
|
|||
for section in config_sections: | |||
config_data[section] = DataGenerator.get_data(section) | |||
config_data['postProcessing'] = NonEmptyDict() |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@p0psicles Don't forget to move these down to the DataGenerator
class below.
@p0psicles any chance this could make it into the next release? |
I think 0.2.7 is realistic |
Hmm that should not have made any difference in snapshot |
I think I made some changes and didn't update snapshots, sorry. |
But your changes still build. After my commit it errored? |
@p0psicles <div class="form-group row">
<h3 class="col-sm-12">Multi-EP sample:</h3>
<div class="example col-sm-12">
<span id="naming_example_multi" class="jumbo"></span>
</div>
</div> |
Waaat.. I checked that after i made the change. Hmm. Maybe it was still cached |
Happy to see the snapshot test is doing its work |
…o make api calls. * Update the snapshots.
I had to do allot more testing on the name-pattern. And fixed some small bugs. It's still not perfect. But working and not making too many api calls. @sharkykh can you do a final check? |
…ages that have not been made responsive yet.
…al post processing settings. * Only show/hide scheduled pp settings with the "scheduled postprocessor" toggle. * used the same bs classes for all the tabs. * Reduced the min-height for component-group class to 100px * Made tab metadata responsive.
<p>Settings that dictate how Medusa should process completed downloads.</p> | ||
<p>The scheduled postprocessor while periodically scan a folder for media to process.</p> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Replace "while" with "will".
* Hide the name-pattern legend, when changing from custom pattern to preset.
Sorry, i have no idea why the backend test is failing? |
Ok great. With one more approval this can be merged. |
Depends on:
Add axios api clients for apiv1 and the normal routes that return json #4258Add vue component name-pattern.mako #4288Todo: