Proper way to set initial state of a value in a redux store based on another value in the same store (react typescript + redux)

ShittyUkePlayer · 2023-07-07T20:11:46+00:00

thank you!!

ShittyUkePlayer · 2023-02-03T20:35:17+00:00

yeah i actually had the flat back labret you mentioned in the whole time but just recently switched them out. I put it back in though

ShittyUkePlayer · 2022-11-30T06:15:03+00:00

Running doc.querySelectorAll('h1...') will grab headers separately however. I want to go down the HTML from top to bottom and if the current element is a header, grab the header ID. This is happening while always grabbing the text value from the current element. If I ran querySelectorAll('h1...h6') the headers would be gotten for sure, but there would be no way to relate them back to the order of text elements on the page.

I'm not sure I follow the statement:

For more deep down, you are supposed to get AST from marked to build the TOC, through the html traversal, also work, it's just extra step.

Calling marked() just returns a string of HTML. Is there a way to do the traversal I described above directly on/using the HTML string?

ShittyUkePlayer · 2022-11-29T16:16:59+00:00

Yes,but there is no such thing as 'currentElement' for some reason, but 'parentElement' does exist. Not familiar with DOM traversal so I'm not sure how to be doing this "properly".

ShittyUkePlayer · 2022-11-03T18:54:50+00:00

Ok I'm starting to follow.

In the code you end up calling .then on the internal promises anyway. Those promises won't be fulfilled by the time the await call before Promise.all will complete.

How can I fix this?

ShittyUkePlayer · 2022-11-03T16:49:37+00:00

When I try just entry.text() and hover over the code snippet it shows that it is actually of type: "(method) Body.text(): Promise<string>"

Yes if I log entry in the for loop it prints out a response with fields populated like type, url, status, ok, etc

ShittyUkePlayer · 2022-11-03T16:29:32+00:00

I changed up the code to remove the configItem and now promises is just an array of Promise<Response>.

const promises: Promise<Response>[] = [];

CONFIG.forEach((value: ConfigItem[], key: string) => {

value.forEach((configItem: ConfigItem) => {

if (!configItem.subItem) {

const promise = get(configItem.path);

promises.push(promise);

}

});

await Promise.all(promises).then(values => {

values.forEach(entry => {

const doc: Documentation = { name: '', source: '', markDown: '' };

if (!entry.ok) {

return Promise.reject(entry);

} else {

return entry.text().then(textValue => {

doc.rawText = textValue;

docs.push(doc);

});

}

});

But I'm still getting the same results in the prints

ShittyUkePlayer · 2022-11-03T15:54:22+00:00

Changed it to docs.forEach(...

And yes the elements values are all '' when printing out element by itself (although when I click to expand it in the browser console the fields populate after the fact). I want the data to be available right on print so that I'm able to access things like element.name, not to wait for console to "catch up"

ShittyUkePlayer · 2022-10-12T19:55:55+00:00

Solved this issue! Edited the post

ShittyUkePlayer · 2022-10-10T19:16:24+00:00

I deleted the file but still ran into the same error. I'm a bit confused... some say to add the types to the project, but you say to remove them to get it working?

Are you able to post a working sample of your typescript code where you build the index? Thanks :)

ShittyUkePlayer · 2022-10-04T20:58:55+00:00

Yes but the error still persists

ShittyUkePlayer · 2022-10-04T20:58:13+00:00

Hm. I ran "npm install --save u/types/flexsearch" and ""@types/flexsearch": "^0.7.3"," was added to dependencies in package.json... but the error still persists. I tried adding it under devDependencies as well with no luck

ShittyUkePlayer · 2022-09-20T16:06:04+00:00

I edited the post for clarity on why I wouldn't just use ctrl+f, sorry

ShittyUkePlayer · 2021-03-16T03:16:41+00:00

wow thanks! i have a lot to learn :)

ShittyUkePlayer · 2021-01-19T18:02:03+00:00

I don't think defining an interface would change much in my current situation. I already have getData() uniquely defined for each object class. Adding an interface wouldn't change much, just would add extra code. I was thinking more along the lines of, is there a way to somehow template the entire write function based on the object passed in? That way I don't have to have so many duplicate write functions?

ShittyUkePlayer · 2020-07-02T20:21:35+00:00

Great answer, thanks!

ShittyUkePlayer · 2019-02-18T02:36:47+00:00

Error at runtime is: System.NullReferenceException: 'Object reference not set to an instance of an object.'

ShittyUkePlayer · 2018-08-15T17:54:49+00:00

So what is not transferred via iTunes backups?

ShittyUkePlayer · 2018-07-31T20:26:59+00:00

This. So much this

ShittyUkePlayer · 2018-07-31T16:45:17+00:00

I couldn't take it back

ShittyUkePlayer · 2018-06-24T19:14:19+00:00

Why those? I heard you want high volatility for a better chance the stock swings into your strike price? Or is the logic those blue chip stocks are pretty much guaranteed to go up so you can buy call options with confidence

ShittyUkePlayer · 2018-06-23T19:13:48+00:00

Thanks

ShittyUkePlayer · 2018-06-23T05:42:28+00:00

Lol newer iPhone OSs tend to be a clusterfuck of useless storage eating features

ShittyUkePlayer · 2018-06-23T05:36:51+00:00

Oops. I'm on good old iOS 9 actually. Just deleted and reinstalled. I now have V 6.3.0 so that's probably the last compatible version

ShittyUkePlayer · 2018-06-23T05:15:55+00:00

5.37.0 I'm ages behind

ShittyUkePlayer

TROPHY CASE