based on #8 (comment) #7

https://github.com/GroceriStar/pdf-export-component/blob/master/src/index.js#L11-L15

This issue lists Renovate updates and detected dependencies. Read the Dependency Dashboard docs to learn more.

Datasource	Name	Replacement PR?
npm	@babel/plugin-proposal-class-properties
npm	babel-preset-es2015
npm	npm-run-all
npm	rollup-plugin-babel
npm	rollup-plugin-commonjs
npm	rollup-plugin-node-resolve
npm	rollup-plugin-replace
npm	rollup-watch

Rate-Limited

These updates are currently rate-limited. Click on a checkbox below to force their creation now.

• chore(deps): replace dependency npm-run-all with npm-run-all2 5.0.0
• chore(deps): replace dependency rollup-plugin-node-resolve with @rollup/plugin-node-resolve 6.0.0
• chore(deps): update dependency standard to v17.1.0
• fix(deps): update dependency @react-pdf/renderer to v2.3.0
• fix(deps): update dependency antd to v4.24.16
• fix(deps): update dependency eslint to v8.57.0
• chore(deps): update dependency babel-plugin-module-resolver to v5
• chore(deps): update dependency browser-sync to v3
• chore(deps): update dependency rollup to v4
• fix(deps): update dependency antd to v5
• fix(deps): update dependency eslint to v9
• fix(deps): update dependency uuid to v10
• 🔐 Create all rate-limited PRs at once 🔐

Edited/Blocked

These updates have been manually edited so Renovate will no longer make changes. To discard all commits and start over, click on a checkbox.

• chore(deps): update dependency coveralls to v3.1.1
• chore(deps): update react monorepo to v18.3.1 (react, react-dom)

Open

These updates have all been created already. Click a checkbox below to force a retry/rebase of any.

• fix(deps): update dependency snyk to v1.1064.0 [security]
• chore(deps): replace dependency rollup-plugin-babel with @rollup/plugin-babel 5.0.0
• chore(deps): update dependency enzyme-adapter-react-16 to v1.15.8
• chore(deps): update dependency jest to v28.1.3
• chore(deps): update babel monorepo (@babel/cli, @babel/core, @babel/plugin-proposal-class-properties, @babel/plugin-proposal-decorators, @babel/plugin-transform-react-jsx-compat, @babel/plugin-transform-react-jsx-self, @babel/plugin-transform-runtime, @babel/preset-env, @babel/preset-react)
• chore(deps): update dependency browser-sync to v2.29.3
• chore(deps): update dependency rollup to v2.79.1
• chore(deps): update dependency jest to v29
• fix(deps): update dependency @react-pdf/renderer to v3
• Click on this checkbox to rebase all open PRs at once

Detected dependencies

• Check this box to trigger a request for Renovate to run again on this repository

#222 (review)

in order to see warnings that we have (we're using module standard, but it's just a wrapper around ESLint) - you need to run yarn code-fix and you'll see warnings that we have
This can be your second task @ronniebhatt

https://travis-ci.org/GroceriStar/pdf-export-component/jobs/480807398
we still getting the same error

#222 (review)

1. make one entry point for importing styles for different types of document styles
2. improve this construction. The goal is to reduce the size of this component, simplify logic and it should work https://github.com/GroceriStar/pdf-export-component/blob/master/src/components/DocumentLayouts.js#L24-L44

Take time, think, review the whole code of the package. There a lot of hints, that should or could help you. If you will not be able to solve this task - that I'm not sure if you're ready to follow my lead @ronniebhatt

Describe the bug
A clear and concise description of what the bug is.

To Reproduce
Steps to reproduce the behavior:

1. Go to '...'
2. Click on '....'
3. Scroll down to '....'
4. See error

Expected behavior
A clear and concise description of what you expected to happen.

Screenshots
If applicable, add screenshots to help explain your problem.

Additional context
Add any other context about the problem here.

GroceriStar/showcase#141

and i also want to have a layout, that will be used for printing single recipe or an array of recipes.

right now i just want to have a separate place, where we'll be able to display one recipe or few if we send an array of data.

so we don't need to have any styles of fanciness. pure data that can be displayed using an object from fetch will suit well.
simple version, i.e. structure you can see here: https://github.com/GroceriStar/showcase/blob/master/src/components/Cell/RecipeLayout.js#L117-L160

• inside DocumentLayouts we should have one of RenderList by passing different type
• DownloadLink -> Button with PDFDownloadLink
• RenderList
• GeneratePDFButton
• ...

example:

describe('<MyComponent />', () => {
  
  it('renders a header', () => {
    const wrapper = shallow(<MyComponent />);
    expect(wrapper.contains(<h1>My Component</h1>)).toBe(true);
  });

  it('renders three <Foo /> components', () => {
    const wrapper = shallow(<MyComponent />);
    expect(wrapper.find(Foo).length).toBe(3);
  });
  
  it('expects to change the status when clicking the button', () => {
    const wrapper = shallow(<MyComponent />);
    
    expect(wrapper.state().status).toBe(false);
    expect(wrapper.contains(<p>Status is {'Off'}</p>)).toBe(true);
  
    wrapper.find('button').simulate('click');
    
    expect(wrapper.state().status).toBe(true);
    expect(wrapper.contains(<p>Status is {'On'}</p>)).toBe(true);
  });
  
});

Describe the bug
A clear and concise description of what the bug is.

To Reproduce
Steps to reproduce the behavior:
sudo npm run build

Expected behavior
A clear and concise description of what you expected to happen.

Screenshots
If applicable, add screenshots to help explain your problem.

Additional context
Add any other context about the problem here.

@groceristar/[email protected] prebuild /home/vadim/work/javascript/pdf-export-component
npm run std --silent

internal/modules/cjs/loader.js:638
throw err;
^

Error: Cannot find module 'prelude-ls'
at Function.Module._resolveFilename (internal/modules/cjs/loader.js:636:15)
at Function.Module._load (internal/modules/cjs/loader.js:562:25)
at Module.require (internal/modules/cjs/loader.js:690:17)
at require (internal/modules/cjs/helpers.js:25:18)
at Object. (/home/vadim/work/javascript/pdf-export-component/node_modules/levn/lib/parse-string.js:4:12)
at Object. (/home/vadim/work/javascript/pdf-export-component/node_modules/levn/lib/parse-string.js:113:4)
at Module._compile (internal/modules/cjs/loader.js:776:30)
at Object.Module._extensions..js (internal/modules/cjs/loader.js:787:10)
at Module.load (internal/modules/cjs/loader.js:653:32)
at tryModuleLoad (internal/modules/cjs/loader.js:593:12)

@groceristar/[email protected] build /home/vadim/work/javascript/pdf-export-component
rollup -c config/prod.js

Error: ENOENT: no such file or directory, lstat '/home/vadim/work/javascript/pdf-export-component/config/prod.js'
at Object.realpathSync (fs.js:1461:7)
at runRollup (/home/vadim/work/javascript/pdf-export-component/node_modules/rollup/bin/rollup:3929:20)
at Object. (/home/vadim/work/javascript/pdf-export-component/node_modules/rollup/bin/rollup:4014:2)
at Module._compile (internal/modules/cjs/loader.js:776:30)
at Object.Module._extensions..js (internal/modules/cjs/loader.js:787:10)
at Module.load (internal/modules/cjs/loader.js:653:32)
at tryModuleLoad (internal/modules/cjs/loader.js:593:12)
at Function.Module._load (internal/modules/cjs/loader.js:585:3)
at Function.Module.runMain (internal/modules/cjs/loader.js:829:12)
at startup (internal/bootstrap/node.js:283:19)
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! @groceristar/[email protected] build: rollup -c config/prod.js
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the @groceristar/[email protected] build script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR! A complete log of this run can be found in:
npm ERR! /home/vadim/.npm/_logs/2019-06-23T20_34_48_241Z-debug.log

• move our logic of generation of pdf into https://github.com/diegomura/react-pdf/tree/master/examples
  it'll also require a separation of our stuff

• we can setup it as hakernoon article. think about it!
  maybe we should have a separated repo with simple install pluss export to sandbox so we can share it easily with people.

doint it here: https://github.com/GroceriStar/react-pdf

it's without header

but when I add header the space between boxes are random like this

all RenderList* components should have *test file with describe, related to passing data attribute.

sample of how we use one fo these components:

<View style={styles.direction}>
            <RenderLists2 data={data} />

          </View>

Note: by default data is array, but pay attention.

we have different layout types.
and this layout types expect a different data structures inside of them. so if layout expect to have an id - we should pass it. if no - then we should alarm about it

at our Document layouts i see this line
but we don't have this files. Am i right that we didn't move them from showcase, right? or we don't need them

https://github.com/MrRio/jsPDF

i think it's obvious task

when i see this import, it's easy to find out what should be improved.
https://github.com/GroceriStar/pdf-export-component/blob/master/src/index.js#L15-L29

So right now we have 4 components that triplicated, because we have 3 different cases for displaying data.
But i also want to have 4th case to add, but this will be a problem - because a lot of code is similar.
I think we should create some sort of a component, where we'll pass a type property and it'll define which case we'll cover.

right now as it passing build, but we should enable dist folder for npm publish - i'm curious to see how it will work at CRA react-print-pdf repository

Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]

Is it was created as task at GitHub issues? Please provide an issue number or link

Describe the solution you'd like
A clear and concise description of what you want to happen.

Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.

Additional context
Add any other context or screenshots about the feature request here.

All is simple:

• review our current codebase
• find out that we have 4 components that doing the same thing
• make one component that will work in our 4 cases
• after publishing on npm - install to react-pdf-sandbox and check is everything working OK
  @hirdbluebird do you want to grab it?

I decide to reduce confusion, it should make our components clearner.
You can see what I did at RenderLists1. Please apply the same logic to our other RenderList components

https://github.com/RelaxedJS/ReLaXed

• https://themeteorchef.com/tutorials/rendering-pdfs-with-react-components
• https://www.npmjs.com/package/generate-pdf
• https://www.npmjs.com/package/html-pdf
• https://stackoverflow.com/questions/41529149/create-pdf-file-from-html-text-react
• https://github.com/eKoopmans/html2pdf
• https://github.com/diegomura/react-pdf
• http://blog.stahlmandesign.com/export-html-to-pdf-how-hard-can-it-be/
• https://freshwebdev.com/react-pdf-create-pdf-file-react-js.html

Some of our test files generate eslint warnings, default to Jest.
In order to skip these warnings, at each of our test file we should add this line: https://github.com/GroceriStar/groceristar-fetch/blob/master/src/projects/GroceriStar/test/files.test.js#L1

feel free to do it and push your changes

I moved maybe everything files, related too our pdf functionality from showcase.
You should check everything after me:
folder structure
import structure, connection between files, etc...

when everything will be good - please run build and publish at npm.
then install this package at https://github.com/GroceriStar/react-print-pdf and recreate the logic that we had at showcase. this will be our major place to test pdf stuff. and when we'll need - we'll update our separated react package - reconnect it here, test and when everything will be perfect - we'll move it into showcase - and clean it up there...

Plus don't forget styles and change import at index...

i just want to compare it and figure out is it better for our needs or not.
http://pdfkit.org/

we just need to create a rules - like what structure our components should receive and then pass this data from the parent components

you just need to replace nice rollup react babel7 setup with this set of repositories

• https://github.com/GroceriStar/antd-showcase-components
• https://github.com/GroceriStar/cards-wrapper-component
• https://github.com/GroceriStar/shoplist-blocks-component
• https://github.com/GroceriStar/grocery-react-component
• https://github.com/GroceriStar/antd-second-components
• https://github.com/GroceriStar/select-component
• https://github.com/ChickenKyiv/meal-form-component

We can also add husky in order to run eslint each commit